applying dev context configuation to test stage#194
applying dev context configuation to test stage#194ravisinha0506 wants to merge 1 commit intoawslabs:mainfrom
Conversation
ellistarn
left a comment
ellistarn
left a comment
There was a problem hiding this comment.
The more time I spend with zap, the more I want to just always use the production logger to standardize tools. It has a nice side effect of leading decs towards making logs that will be readable in production.
Thoughts?
|
My 2c is that there's a lot of value in being able to configure lower logging levels for troubleshooting application behavior. I think having the ability to explicitly set logging level (instead of using stage as a proxy) has the advantage of being able to activate debug logging in select production scenarios where there's a need to debug customer specific behavior. |
Completely agree. If we're just using I like James' suggestion as it keeps us as "production-like" as possible in development, while giving us the control we need. |
3 participants
Issue #, if available:
Description of changes:
Most of the dev stages are configured as
teststage. As per existing code, test stage utilizes prod configuration. Hence, applying dev stage configuration to test stage as wellBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.